Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

staging-next 2024-05-15 - last for 24.05 #312133

Merged
merged 201 commits into from
May 21, 2024
Merged

staging-next 2024-05-15 - last for 24.05 #312133

merged 201 commits into from
May 21, 2024

Conversation

vcunat
Copy link
Member

@vcunat vcunat commented May 16, 2024

This is the last staging-next iteration that will reach 24.05. (But there will be staging*-24.05 afterwards, as usual.)

There should be no breaking changes in this one (desktops have an exception but probably unused now).

Helpful links

Mass breakages

nothing notable so far

rhelmot and others added 30 commits March 24, 2024 12:27
in the new release the meson option `systemdsystemunitdir` is broken by
the new `sysusers.d` code in `meson.build`. we fix this by setting both
of these pkg-config variables through environment variables.

Changes: polkit-org/polkit@123...124
since the repo at gitlab.fredesktop.org is archived, it's likely safer
to pull down this patch into nixpkgs directly. in case the archived repo
vanishes in the future.
Add a test where a conflicting package can be found at the end of
multiple dependency chains. This is far too simple an example to
demonstrate the ill effects of exponential time complexity, but does
serve to demonstrate how the error output changes when each path is only
visited once.
The hook performs a depth first search on the graph defined by
propagatedBuildInputs. This traverses all paths through the graph,
except for any cycles. In the worst case with a highly connected graph,
this search can take exponential time. In practice, this means that in
cases with long dependency chains and multiple packages depending on the
same package, the hook can take several hours to run.

Avoid this problem by keeping track of already visited paths and only
visiting each path once. This makes the search complete in linear time.

The visible effect of this change is that, if a conflict is found, only
one dependency chain that leads to the conflicting package is printed,
rather than all the possible dependency chains.
Now that we only visit each path once, a few things can be simplified.
We no longer have to keep a list of different dependency chains leading
to a package, since only one chain will ever be found. Also, the already
visited check also takes care of cycles, so the other cycle check can be
removed.
…itespace

Currently, nix-support/propagated-build-inputs is parsed by splitting on
a single space. This means that if this file contains multiple spaces
separating two paths, the build_inputs list will end up containing an
empty string.

Instead, call split() with no arguments, which splits on runs of
whitespace and also ignores whitespace at the beginning and end of the
string, eliminating the need for strip().
Using python3Minimal avoids infinite recursions in the stdenv bootstrap on x86_64-darwin when building Python with configd support.
2.42.11 disables several loaders by default. The meson option "others" reenables
these for packages that still depend on them.
The "others" option includes ani which is currently affected by CVE-2022-48622.
Disable this by removing it from the build while allowing the other loaders
to build.
[staging] libcamera: fix binary reproduciblity
Instead of assuming that systemd is desired whenever it is availabe, introduce
flag that allows disabling systemd. This flag is still defaults to true as long
as systemd is available on the host platform.

This is no-rebuild change.
musl 1.2.5 no longer provides the GNU version.

Upstream is dead so patching is probably our only option, but at least
that means it's unlikely to break in a future release!
apple-source-releases: always use python3Minimal
wegank and others added 7 commits May 20, 2024 00:30
We're running into multiple issues, so let's be conservative.
In particular, this commit should fix *-darwin builds.
/cc PR #309805 as this is kind-of reverting it (partially for now)
@vcunat vcunat mentioned this pull request May 21, 2024
13 tasks
@vcunat
Copy link
Member Author

vcunat commented May 21, 2024

Linux regressions seem merge-able to me. Just one thing really caught my eye (not a merge blocker):

Darwin is still missing quite a lot of binaries, but I hope it will all be fine to merge later today.

@vcunat
Copy link
Member Author

vcunat commented May 21, 2024

@vcunat vcunat merged commit e40d38e into master May 21, 2024
6 of 7 checks passed
@vcunat vcunat mentioned this pull request May 31, 2024
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.